fix(bundler): keep compiled renderer service live - #3690

Summary

Fixes compiled renderer startup when the Node-compatible ChildProcess reports exitCode and signalCode as undefined before exit. The esbuild adapter previously treated that live service as externally owned, permanently rejecting TSX transforms and returning preview HTTP 500s.

Root cause

Staging renderer logs from strict E2E run #31756302514 show project TSX transforms failing with [ext-bundler-esbuild] Cannot own an esbuild service started outside the module-wide adapter. The production Deno-compiled runtime exposes unset exit fields during service startup; the adapter accepted only null.

Validation

• Added a regression test for Node-compatible unset exit fields.
• deno test --no-check --allow-all extensions/ext-bundler-esbuild/src/esbuild-bundler.test.ts — 6 tests / 19 steps passed.
• deno fmt --check and git diff --check passed.

Validation gap

The local compiled-binary test and repository typecheck are blocked before test execution by the local Deno 2.9.4 runtime lacking the repository-required node:util/types brand checks; CI runs in the supported environment and is the release gate.

Summary by CodeRabbit

• Bug Fixes

  • Improved detection of active esbuild processes across runtimes that report missing exit or signal information.
  • Prevented active bundler services from being incorrectly treated as stopped.

• Tests

  • Added coverage for identifying a running child process with undefined exit details.